Saving Executable Modules
An executable module (EM) is the end result of compiling a process. It is the APPX-executable format that is generated by the process compiler, and accessed by the process loader and process interpreter to execute the process. A process is automatically verified and compiled by APPX when the process is loaded.
To avoid verifying and compiling a process each time it is loaded, and thereby increase performance, you can elect to save an EM on disk. Once an EM is compiled and saved, APPX refers to the saved EM during execution. The process loader, however, verifies that the saved EM is current. If changes to application specifications make the EM obsolete, APPX automatically generates a new EM.
Each EM is automatically assigned an eight-character alphanumeric file name. This unique string is never changed. If APPX finds it necessary to recreate an existing EM, the new EM retains the same file name.
You can designate whether or not you want to save EMs at the installation, application, and process levels. You establish installation and application values in system administration. You can optionally override these designations for each individual process in application design. If you leave a process specification blank, the application value is assumed. If both are blank, the installation value is assumed.
There is a cost associated with saving an EM; it consumes disk space. This trade-off must be evaluated based upon the specifics of each installation. As a general rule, however, EMs should be saved for larger processes, because they require significant compile time. For smaller processes that are relatively quick to compile, the consumption of additional disk space may not be warranted.
Refer to Process Definition, for Executable Module -- Save on Disk? specifications. |